home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Patches 1995 March
/
SGI IRIX Patches 1995 Mar.iso
/
relnotes
/
patchSG0000304
/
ch1.z
/
ch1
Wrap
Text File
|
1995-03-10
|
5KB
|
199 lines
- 1 -
1. _P_a_t_c_h__S_G_3_0_4__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG304 to IRIX 5.3
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for all platforms.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IDO 5.3 running under IRIX
5.3. It is not meant to be installed on systems running IDO
5.3 under the IRIX 5.3 with XFS release. This patch
conflicts with any patch for SGI's SCR # 253016 released for
that software configuration.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_3_0_4
This patch contains fixes for the following bugs in IRIX
5.3. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
+o BUG 259744: aio.h header file broken when used with C++
and MIPS ABI async I/O.
+o BUG 254955: using multiple sprocs with the libabi
aio_* functions could cause user program deadlocks. To
solve this problem user programs using multiple sprocs
must set the number of sprocs in their program in the
aio_numusers item of the struct aioinit passed to
aio_sgi_init. This call to aio_sgi_init must happen
before any other aio_* or lio_listio calls.
1.4 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_3_0_4
This patch release includes these subsystems:
+o patchSG0000304.dev_hdr.lib
This patch only corrects problems in the development of
programs using libabi async I/O. To get the complete patch
you need the latest patch to eoe1.sw.irix_lib that contains
fixes for the following bugs in the runtime of libabi async
I/O:
+o Bug 254719
+o Bug 256769
- 2 -
+o Bug 250515
+o Bug 254955
+o Bug 256479
1.5 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed in
this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
_i_n_s_t.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _S_o_f_t_w_a_r_e
_I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst>prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Select the desired patches for installation.
3. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
4. You may find that two patches have been marked as
incompatible. If this occurs, you must deselect one
of the patches.
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
5. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
- 3 -
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.